System and method for implementing added services for obd2 smart vehicle connection

ABSTRACT

Novel tools and techniques might provide for implementing Internet of Things (“IoT”) functionality, and, in particular embodiments, implementing added services for OBD2 connection for IoT-capable vehicles. In various embodiments, a portable device (when connected to an OBD2 DLC port of a vehicle) might monitor wireless communications between a vehicle computing system(s) and an external device(s), might monitor vehicle sensor data from vehicular sensors tracking operational conditions of the vehicle, and might monitor operator input sensor data from operator input sensors tracking input by a vehicle operator. The portable device (or a server) might analyze either the monitored wireless communications or a combination of the monitored vehicle sensor data and the monitored operator input sensor data, to determine whether vehicle operation has been compromised. If so, the portable device (or the server) might alert the operator of the vehicle via a user interface, and might initiate one or more remediation operations.

CROSS-REFERENCES TO RELATED APPLICATIONS COPYRIGHT STATEMENT

A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

FIELD

The present disclosure relates, in general, to methods, systems, apparatus, and computer software for implementing Internet of Things (“IoT”) functionality, and, in particular embodiments, to methods, systems, apparatus, and computer software for implementing added services for OBD2 connection for IoT-capable vehicles.

BACKGROUND

As vehicles become more connected with other devices and systems (e.g., due to proliferation of Internet of Things (“IoT”) functionality, due to adding non-IoT wireless communications capabilities to the vehicles, and/or the like), these so-called “smart vehicles” become susceptible to external influence (such as hackers attempting intrusion into the vehicle systems, hackers planting viruses or other malicious software (“malware”) that infect the vehicle systems, or malware-infected devices (perhaps even associated with the operator of the vehicle or passengers therein) being “innocently” connected to the vehicle systems thereby infecting them, and/or the like). Further due to modern vehicles operating by “fly-by-wire” systems (i.e., using electronic connections, rather than mechanical linkages, between the control systems of the vehicle (e.g., accelerator pedal, brake pedal, steering wheel, and/or the like) and the corresponding operational systems of the vehicle (e.g., engine or throttle valve, brakes, variable power assist system, and/or the like), in conjunction with the potential security issues that exist with wireless communications, it becomes possible for third parties to remotely control the vehicle or otherwise detrimentally affect the operation of the vehicle. Currently, there do not appear to be systems in place to remedy such occurrences, much less systems or methods that provide added services via OBD2 connection to remedy such occurrences.

Hence, there is a need for more robust and scalable solutions for implementing communications for Internet of Things (“IoT”) functionality, and, in particular embodiments, to methods, systems, apparatus, and computer software for implementing added services for OBD2 connection for IoT-capable vehicles.

BRIEF DESCRIPTION OF THE DRAWINGS

A further understanding of the nature and advantages of particular embodiments may be realized by reference to the remaining portions of the specification and the drawings, in which like reference numerals are used to refer to similar components. In some instances, a sub-label is associated with a reference numeral to denote one of multiple similar components. When reference is made to a reference numeral without specification to an existing sub-label, it is intended to refer to all such multiple similar components.

FIG. 1 is a schematic diagram illustrating a system for implementing added services for OBD2 connection for Internet of Things (“IoT”)-capable vehicles, in accordance with various embodiments.

FIG. 2 is a schematic diagram illustrating the portable device of the system of FIG. 1 in the context of a system for implementing added services for OBD2 connection for IoT-capable vehicles, in accordance with various embodiments.

FIG. 3 is a block diagram illustrating the various components of the vehicle of the system of FIG. 1 in the context of implementing added services for OBD2 connection for IoT-capable vehicles, in accordance with various embodiments.

FIG. 4 is a schematic diagram illustrating the various components of the vehicle of the system of FIG. 1 in the context of implementing added services for OBD2 connection for IoT-capable vehicles, in accordance with various embodiments.

FIGS. 5A-5C are flow diagrams illustrating a method for implementing added services for OBD2 connection for IoT-capable vehicles, in accordance with various embodiments.

FIG. 6 is a block diagram illustrating an exemplary computer or system hardware architecture, in accordance with various embodiments.

FIG. 7 is a block diagram illustrating a networked system of computers, computing systems, or system hardware architecture, which can be used in accordance with various embodiments.

DETAILED DESCRIPTION OF CERTAIN EMBODIMENTS Overview

Various embodiments provide tools and techniques for implementing Internet of Things (“IoT”) functionality, and, in particular embodiments, to methods, systems, apparatus, and computer software for implementing added services for OBD2 connection for IoT-capable vehicles.

In various embodiments, a portable device (when connected to, or plugged into, on-board diagnostics (“OBD2”) data link connector (“DLC”) port of a vehicle) might monitor wireless communications between at least one vehicle computing system and at least one external device (which might include remote devices associated with hackers or malware-infected devices associated with one of the occupants of the vehicle, or the like), might monitor one or more vehicle sensor data from one or more vehicular sensors tracking operational conditions of the vehicle, and might monitor one or more operator input sensor data from one or more operator input sensors tracking operator input by an operator of the vehicle. The portable device (or a server) might analyze either the monitored wireless communications or a combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised. Based on a determination that vehicle operation has been compromised, the portable device (or the server) might alert the operator of the vehicle regarding the vehicle operation being compromised, using the portable device via a user interface, and might initiate one or more remediation operations.

In some embodiments, the one or more sensors tracking operational conditions of the vehicle might include, without limitation, at least one of one or more engine speed sensors, one or more engine air flow sensors, one or more air-fuel mixture sensors, one or more vehicle speed sensors, one or more brake actuator sensors, one or more vehicle traction sensors, one or more vehicle stability sensors, one or more vehicle body motion sensors, and/or the like. The one or more operator input sensors tracking operator input by the operator of the vehicle might include, without limitation, at least one of one or more accelerator pedal position sensors, one or more cruise control switch sensors, one or more brake pedal position sensors, one or more steering angle sensors, and/or the like.

According to some embodiments, the user interface might be embodied within (or on an exterior surface) of the portable device (such as the one or more buttons (either soft/virtual buttons or physical buttons, or the like), switches, toggles, display devices, key pads, or the other input/output devices, or the like), might be embodied within a user interface device that is part of the vehicle (e.g., a dash-mounted display device, a speaker system of the vehicle, the instrument cluster, a heads-up display, and/or the like), and/or might be embodied within at least one user device (including, but not limited to, a laptop computer, a tablet computer, a smart phone, a mobile phone, a portable gaming device, and/or the like) that is associated with the operator (or associated with a passenger of) the vehicle, and/or the like.

The various embodiments herein (as described in detail with respect to the figures) provide solutions: to prevent infection of the vehicle computing system, the vehicular sensors, and/or the operational systems by viruses or other malware; to prevent intrusion attempts by third parties (or hackers, etc.) to remotely control the vehicle; to detect and remove any viruses or other malware that have already infected the vehicle computing system, the vehicular sensors, and/or the operational systems; to restore settings and configurations of the vehicle computing system, the vehicular sensors, and/or the operational systems to previous (uninfected, optimal, or operational) settings and configurations in the case that the viruses, other malware, or intrusion attempts have detrimentally changed or affected the settings and configurations of the vehicle computing system, the vehicular sensors, and/or the operational systems. The various embodiments, in some cases, might also provide encryption functionalities to protect sensor data, control data, or other data used by the various vehicle systems; provide firmware validation functionalities for the firmware of the vehicle computing system, the vehicular sensors, and/or the operational systems; provide custom routing functionality for communications routes amongst the vehicle computing system, the vehicular sensors, and/or the operational systems; and/or the like.

The following detailed description illustrates a few exemplary embodiments in further detail to enable one of skill in the art to practice such embodiments. The described examples are provided for illustrative purposes and are not intended to limit the scope of the invention.

In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the described embodiments. It will be apparent to one skilled in the art, however, that other embodiments of the present invention may be practiced without some of these specific details. In other instances, certain structures and devices are shown in block diagram form. Several embodiments are described herein, and while various features are ascribed to different embodiments, it should be appreciated that the features described with respect to one embodiment may be incorporated with other embodiments as well. By the same token, however, no single feature or features of any described embodiment should be considered essential to every embodiment of the invention, as other embodiments of the invention may omit such features.

Unless otherwise indicated, all numbers used herein to express quantities, dimensions, and so forth used should be understood as being modified in all instances by the term “about.” In this application, the use of the singular includes the plural unless specifically stated otherwise, and use of the terms “and” and “or” means “and/or” unless otherwise indicated. Moreover, the use of the term “including,” as well as other forms, such as “includes” and “included,” should be considered non-exclusive. Also, terms such as “element” or “component” encompass both elements and components comprising one unit and elements and components that comprise more than one unit, unless specifically stated otherwise.

The tools provided by various embodiments include, without limitation, methods, systems, and/or software products. Merely by way of example, a method might comprise one or more procedures, any or all of which are executed by a computer system. Correspondingly, an embodiment might provide a computer system configured with instructions to perform one or more procedures in accordance with methods provided by various other embodiments. Similarly, a computer program might comprise a set of instructions that are executable by a computer system (and/or a processor therein) to perform such operations. In many cases, such software programs are encoded on physical, tangible, and/or non-transitory computer readable media (such as, to name but a few examples, optical media, magnetic media, and/or the like).

Various embodiments described herein, while embodying (in some cases) software products, computer-performed methods, and/or computer systems, represent tangible, concrete improvements to existing technological areas, including, without limitation, vehicle communications technology, IoT communications technology, network security technology for vehicles, and/or the like. In other aspects, certain embodiments, can improve the functioning of user equipment or systems themselves (e.g., telecommunications equipment, network components, etc.), for example, by monitoring, with a portable device via an OBD2 DLC port of a vehicle, wireless communications between at least one vehicle computing system and at least one external device, monitoring, with the portable device via the OBD2 DLC port, one or more vehicle sensor data from one or more vehicular sensors tracking operational conditions of the vehicle, monitoring, with the portable device via the OBD2 DLC port, one or more operator input sensor data from one or more operator input sensors tracking operator input by an operator of the vehicle, analyzing, with the portable device (and/or a remote server), either the monitored wireless communications or a combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised, and (if so) initiating, with the portable device, one or more remediation operations (including, but not limited to, disrupting (and in some cases, jamming) some or all wireless communications to/from the vehicle, reconnecting authorized wireless communications, detecting and blocking malware or intrusion attempts via the wireless communications, detecting and removing any malware that have infected the vehicle systems, encrypting and storing vehicle data, sensor data, and/or other data, validating firmware of the vehicle systems, restoring settings and configurations for the (affected or malfunctioning) vehicle systems, providing custom routing functionalities for the vehicle systems, and/or the like). In particular, to the extent any abstract concepts are present in the various embodiments, those concepts can be implemented as described herein by devices, software, systems, and methods that involve specific novel functionality (e.g., steps or operations), such as monitoring wireless communications between at least one vehicle computing system and at least one external device, monitoring one or more vehicle sensor data from one or more vehicular sensors tracking operational conditions of the vehicle, monitoring one or more operator input sensor data from one or more operator input sensors tracking operator input by an operator of the vehicle, analyzing either the monitored wireless communications or a combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised, and (if so) initiating one or more remediation operations, and/or the like, to name a few examples, that extend beyond mere conventional computer processing operations. These functionalities can produce tangible results outside of the implementing computer system, including, merely by way of example, proactively securing the vehicle environment and vehicle systems from wireless access and remote disruption of vehicle operations, while assuring driver safety to the extent possible, which may be observed or measured by customers and/or service providers.

In an aspect, a method might comprise monitoring, with a portable device in communication with one or more computing systems of a vehicle via an on-board diagnostics (“OBD2”) data link connector (“DLC”) port, wireless communications between at least one vehicle computing system of the one or more computing systems of the vehicle and at least one device external to the vehicle; monitoring, with the portable device via the OBD2 DLC port, one or more vehicle sensor data from one or more vehicular sensors tracking operational conditions of the vehicle; and monitoring, with the portable device via the OBD2 DLC port, one or more operator input sensor data from one or more operator input sensors tracking operator input by an operator of the vehicle. The method might further comprise analyzing, with the portable device, at least one of the monitored wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle or a combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised; based on a determination that vehicle operation has been compromised, alerting the operator of the vehicle regarding the vehicle operation being compromised, using the portable device via a user interface; and initiating, with the portable device, one or more remediation operations.

In some embodiments, the one or more computing systems of the vehicle might comprise at least one of an electronic control unit (“ECU”), an electronic control module (“ECM”), an electronic throttle control (“ETC”) system, an electronic stability control (“ESC”) system, a variable-assist power steering system, an automatic steering system, an anti-lock braking system (“ABS”), or a vehicular computing node, and/or the like. In some cases, the one or more vehicular sensors might comprise at least one of one or more accelerator pedal position sensors, one or more engine speed sensors, one or more engine air flow sensors, one or more air-fuel mixture sensors, one or more vehicle speed sensors, one or more cruise control switch sensors, one or more brake pedal position sensors, one or more brake actuator sensors, one or more vehicle traction sensors, one or more vehicle stability sensors, one or more vehicle body motion sensors, or one or more steering angle sensors, and/or the like.

According to some embodiments, analyzing the combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data might comprise analyzing, with the portable device, the one or more vehicle sensor data and the one or more operator input sensor data to determine whether the one or more vehicle sensor data indicates operational conditions of the vehicle that are inconsistent with the corresponding one or more operator input sensor data.

In some instances, the vehicle is an Internet of Things (“IoT”)-capable vehicle and the at least one device external to the vehicle might comprise at least one IoT-capable device, and the wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle might comprise machine-to-machine IoT communications. In some embodiments, the portable device might be an IoT gateway through which all IoT communications pass, and initiating the one or more remediation operations might comprise, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the machine-to-machine IoT communications and based on the operator action comprising disconnecting the portable device from the OBD2 DLC port, disrupting, with the portable device, communication between the at least one vehicle computing system and the at least one device external to the vehicle. In such embodiments, the method might further comprise, in response to the operator reconnecting the portable device into the OBD2 DLC port, establishing, with the portable device, communication between the at least one vehicle computing system and one or more telematics sources. Alternative to disconnecting the portable device from the OBD2 DLC port, the portable device (which might be an IoT gateway through which all IoT communications pass) might comprise a block-wireless-communications button, and initiating the one or more remediation operations might comprise, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the machine-to-machine IoT communications and based on the operator action comprising depressing the block-wireless-communications button on the portable device, disrupting, with the portable device, communication between the at least one vehicle computing system and the at least one device external to the vehicle.

Regardless of whether or not all wireless communications pass through the portable device, where the portable device comprises a block-wireless-communications button, initiating the one or more remediation operations might comprise, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the wireless communications and based on the operator action comprising depressing the block-wireless-communications button on the portable device, disrupting, with the portable device, communication between the at least one vehicle computing system and the at least one device external to the vehicle by jamming all wireless communications within at least one set of telecommunications frequency ranges to and from the vehicle.

Alternatively, or additionally, the portable device might comprise a restore button, and initiating the one or more remediation operations might comprise, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the wireless communications and based on the operator action comprising depressing the restore button on the portable device, restoring, with the portable device, settings and configurations for at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors, and/or the like. In some cases, the settings and configurations for the at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors, and/or the like might comprise one of factory settings and configurations or previously saved settings and configurations, or the like.

Merely by way of example, in some cases, the method might further comprise encrypting, with the portable device, the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, and storing, with the portable device, the encrypted one or more vehicle sensor data and the encrypted one or more operator input sensor data in a local data storage device of the portable device. In some instances, encrypting and storing the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data might be performed either before or after analyzing the at least one of the monitored wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle or the combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised. In some embodiments, encrypting the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data might comprise encrypting, with the portable device, the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, using one or more cryptographic protocols or techniques comprising AES symmetric-key algorithm, Diffie-Hellman key exchange, SHA-1 hash function, forward secrecy, deniable authentication, or malleable encryption, and/or the like.

According to some embodiments, analyzing the at least one of the monitored wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle or the combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised might comprise detecting, with the portable device, whether the wireless communications comprises at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software, and/or the like, and blocking, with the portable device, the at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software, and/or the like from infecting the at least one vehicle computing system via the wireless communications.

In some embodiments, the method might further comprise detecting, with the portable device, whether at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors, and/or the like comprises at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software; and removing, with the portable device, the at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software from the at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors, and/or the like. According to some embodiments, the method might further comprise validating, with the portable device, firmware of at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors.

In another aspect, a portable device might comprise an on-board diagnostics (“OBD2”) data link connector (“DLC”) in communication with one or more computing systems of a vehicle via an OBD2 DLC port of the vehicle; at least one processor; a data storage device; and a non-transitory computer readable medium communicatively coupled to the at least one processor. The non-transitory computer readable medium might have stored thereon computer software comprising a set of instructions that, when executed by the at least one processor, causes the portable device to: monitor, via the OBD2 DLC port, wireless communications between at least one vehicle computing system of the one or more computing systems of the vehicle and at least one device external to the vehicle; monitor, via the OBD2 DLC port, one or more vehicle sensor data from one or more vehicular sensors tracking operational conditions of the vehicle; monitor, via the OBD2 DLC port, one or more operator input sensor data from one or more operator input sensors tracking operator input by an operator of the vehicle; analyze at least one of the monitored wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle or a combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised; based on a determination that vehicle operation has been compromised, alert the operator of the vehicle regarding the vehicle operation being compromised; and initiate one or more remediation operations.

In some embodiments, the one or more computing systems of the vehicle might comprise at least one of an electronic control unit (“ECU”), an electronic control module (“ECM”), an electronic throttle control (“ETC”) system, an electronic stability control (“ESC”) system, a variable-assist power steering system, an automatic steering system, an anti-lock braking system (“ABS”), or a vehicular computing node, and/or the like. In some cases, the one or more vehicular sensors might comprise at least one of one or more accelerator pedal position sensors, one or more engine speed sensors, one or more engine air flow sensors, one or more air-fuel mixture sensors, one or more vehicle speed sensors, one or more cruise control switch sensors, one or more brake pedal position sensors, one or more brake actuator sensors, one or more vehicle traction sensors, one or more vehicle stability sensors, one or more vehicle body motion sensors, or one or more steering angle sensors, and/or the like.

According to some embodiments, analyzing the combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data might comprise analyzing, with the portable device, the one or more vehicle sensor data and the one or more operator input sensor data to determine whether the one or more vehicle sensor data indicates operational conditions of the vehicle that are inconsistent with the corresponding one or more operator input sensor data.

In some instances, the vehicle is an Internet of Things (“IoT”)-capable vehicle and the at least one device external to the vehicle might comprise at least one IoT-capable device, and the wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle might comprise machine-to-machine IoT communications. In some embodiments, the portable device might be an IoT gateway through which all IoT communications pass, and initiating the one or more remediation operations might comprise, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the machine-to-machine IoT communications and based on the operator action comprising disconnecting the portable device from the OBD2 DLC port, disrupting, with the portable device, communication between the at least one vehicle computing system and the at least one device external to the vehicle. In such embodiments, the set of instructions, when executed by the at least one processor, further causes the portable device to: in response to the portable device being reconnected into the OBD2 DLC port, establish communication between the at least one vehicle computing system and one or more telematics sources. Alternative to disconnecting the portable device from the OBD2 DLC port, the portable device (which might be an IoT gateway through which all IoT communications pass) might further comprise a block-wireless-communications button, and initiating the one or more remediation operations might comprise, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the machine-to-machine IoT communications and based on the operator action comprising depressing the block-wireless-communications button on the portable device, disrupting communication between the at least one vehicle computing system and the at least one device external to the vehicle.

Regardless of whether or not all wireless communications pass through the portable device, the portable device might further comprise a block-wireless-communications button and a frequency jamming transmitter, and initiating the one or more remediation operations might comprise, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the wireless communications and based on the operator action comprising depressing the block-wireless-communications button on the portable device, disrupting communication between the at least one vehicle computing system and the at least one device external to the vehicle by jamming, via the frequency jamming transmitter, all wireless communications within at least one set of telecommunications frequency ranges to and from the vehicle.

Alternatively, or additionally, the portable device might further comprise a restore button, and initiating the one or more remediation operations might comprise, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the wireless communications and based on the operator action comprising depressing the restore button on the portable device, restoring settings and configurations for at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors, and/or the like. In some cases, the settings and configurations for the at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors, and/or the like might comprise one of factory settings and configurations or previously saved settings and configurations, or the like.

Merely by way of example, in some cases, the set of instructions, when executed by the at least one processor, further causes the portable device to: encrypt the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data and store the encrypted one or more vehicle sensor data and the encrypted one or more operator input sensor data in the data storage device of the portable device. In some instances, encrypting and storing the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data might be performed either before or after analyzing the at least one of the monitored wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle or the combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised. In some embodiments, encrypting the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data might comprise encrypting the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, using one or more cryptographic protocols or techniques comprising AES symmetric-key algorithm, Diffie-Hellman key exchange, SHA-1 hash function, forward secrecy, deniable authentication, or malleable encryption, and/or the like.

According to some embodiments, analyzing the at least one of the monitored wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle or the combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised might comprise detecting whether the wireless communications comprises at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software, and/or the like, and blocking the at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software, and/or the like from infecting the at least one vehicle computing system via the wireless communications.

In some embodiments, the set of instructions, when executed by the at least one processor, further causes the portable device to: detect whether at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors, and/or the like comprises at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software, and/or the like; and remove the at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software, and/or the like from the at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors, and/or the like. According to some embodiments, the set of instructions, when executed by the at least one processor, further causes the portable device to: validate firmware of at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors.

Various modifications and additions can be made to the embodiments discussed without departing from the scope of the invention. For example, while the embodiments described above refer to particular features, the scope of this invention also includes embodiments having different combination of features and embodiments that do not include all of the above described features.

Specific Exemplary Embodiments

We now turn to the embodiments as illustrated by the drawings. FIGS. 1-7 illustrate some of the features of the method, system, and apparatus for implementing Internet of Things (“IoT”) functionality, and, in particular embodiments, to methods, systems, apparatus, and computer software for implementing added services for OBD2 connection for IoT-capable vehicles, as referred to above. The methods, systems, and apparatuses illustrated by FIGS. 1-7 refer to examples of different embodiments that include various components and steps, which can be considered alternatives or which can be used in conjunction with one another in the various embodiments. The description of the illustrated methods, systems, and apparatuses shown in FIGS. 1-7 is provided for purposes of illustration and should not be considered to limit the scope of the different embodiments.

With reference to the figures, FIG. 1 is a schematic diagram illustrating a system 100 for implementing added services for OBD2 connection for Internet of Things (“IoT”)-capable vehicles, in accordance with various embodiments. In the non-limiting embodiment of FIG. 1 , system 100 might comprise a portable device 105, a vehicle 110, and an on-board diagnostics (“OBD2”) data link connector (“DLC”) port 115 (also referred to as an “OBD2 port” or the like). The OBD2 DLC port 115 is located within the vehicle 110 (and is located within reach of the driver or operator of the vehicle, typically within two feet (or about 61 cm) of the steering wheel). The portable device 105—which is described in detail below with respect to FIG. 2 —is configured to physically couple or connect with the OBD2 DLC port 115 via connector 120. The vehicle 110 might comprise a car, minivan, pickup truck, a police vehicle, a fire engine, an ambulance, a recreational vehicle, a semi-tractor-trailer truck, a commercial truck, a bus, or any other vehicle that has an OBD2 DLC port, and/or the like.

In some embodiments, the vehicle 110 might further comprise one or more vehicle computing systems 125, one or more vehicular sensors 130, and one or more vehicle operational systems 135 (collectively, “vehicle systems”), which are described in greater detail with respect to FIGS. 3 and 4 . The OBD2 DLC port 115 might communicatively couple to each of the one or more vehicle computing systems 125, the one or more vehicular sensors 130, and the one or more vehicle operational systems 135 via a controller area network (“CAN”) bus 140. In some cases, the one or more vehicle computing systems 125 might include, but are not limited to, at least one of an electronic control unit (“ECU”), an electronic control module (“ECM”), an electronic throttle control (“ETC”) system, an electronic stability control (“ESC”) system, a variable-assist power steering system, an automatic steering system, an anti-lock braking system (“ABS”), or a vehicular computing node, and/or the like. In some instances, the one or more vehicular sensors 130 might include one or more sensors tracking operational conditions of the vehicle and one or more operator input sensors tracking operator input by the operator of the vehicle. The one or more sensors tracking operational conditions of the vehicle might include, without limitation, at least one of one or more engine speed sensors, one or more engine air flow sensors, one or more air-fuel mixture sensors, one or more vehicle speed sensors, one or more brake actuator sensors, one or more vehicle traction sensors, one or more vehicle stability sensors, one or more vehicle body motion sensors, and/or the like. The one or more operator input sensors tracking operator input by the operator of the vehicle might include, without limitation, at least one of one or more accelerator pedal position sensors, one or more cruise control switch sensors, one or more brake pedal position sensors, one or more steering angle sensors, and/or the like. The one or more vehicle operational systems 135, in some cases, might include, but are not limited to, at least one of an accelerator pedal, an engine, a throttle valve, a steering wheel, one or more brakes, one or more tires, a brake pedal, or other operational systems, and/or the like.

In some cases, the vehicle might further comprise an (optional) wireless transceiver 145, which might communicatively couple, via the CAN bus 140, to each of the one or more vehicle computing systems 125, the one or more vehicular sensors 130, and the one or more vehicle operational systems 135. According to some embodiments, system 100 might further comprise one or more third party devices 150 and associated databases 155, one or more networks 160, and one or more telecommunications relay systems 165 a, and/or the like. The system 100 might, in some instances, further comprise a service provider network(s) 170 associated with a service provider, a remote server 175, which may also be associated with the service provider, a database(s) or data lake 180 associated with the service provider, and one or more telecommunications relay systems 165 b, and/or the like. In some cases, the networks 160 and 170 might each include, but is not limited to, one or more of a local area network (“LAN”), a wide area network (“WAN”), a wireless wide area network (“WWAN”), a virtual private network (“VPN”), the Internet, or an extranet, and/or the like. Other networks that can be implemented as network 160 or 170 are described below with reference to FIG. 7 . The one or more telecommunications relay systems 165 a or 165 b might each include, without limitation, one or more wireless network interfaces (e.g., wireless modems, wireless access points, and the like), one or more towers, one or more satellites, and/or the like.

The wireless transceiver 145 might provide wireless access to sensor data, command data, updates, etc. for at least one of the one or more vehicle computing systems 125, the one or more vehicular sensors 130, and the one or more vehicle operational systems 135, or might provide an external user device (e.g., third party device(s) 150, user devices associated with the user (as shown in FIG. 7 ), and/or the like), server (e.g., remote server 175, or the like), or other computing system with access, via wireless communication (in some cases, via network(s) 160, via service provider network(s) 170, via one or more telecommunications relay systems 165 a and/or 165 b, and/or the like), to at least one of the one or more vehicle computing systems 125, the one or more vehicular sensors 130, and the one or more vehicle operational systems 135.

In operation, the portable device 105 (when connected to, or plugged into, the OBD2 DLC port 115) might monitor wireless communications between at least one vehicle computing system of the one or more vehicle computing systems 125 (or the vehicle systems collectively) and at least one third party device 150 (or other device external to the vehicle 110). The portable device 105 (when connected to, or plugged into, the OBD2 DLC port 115) might also monitor one or more vehicle sensor data from one or more vehicular sensors 130 (which might include, without limitation, at least one of one or more engine speed sensors, one or more engine air flow sensors, one or more air-fuel mixture sensors, one or more vehicle speed sensors, one or more brake actuator sensors, one or more vehicle traction sensors, one or more vehicle stability sensors, one or more vehicle body motion sensors, and/or the like) tracking operational conditions of the vehicle (i.e., conditions of the one or more vehicle operational systems 135 or the like) and might also monitor one or more operator input sensor data from one or more operator input sensors 130 (including, but not limited to, at least one of one or more accelerator pedal position sensors, one or more cruise control switch sensors, one or more brake pedal position sensors, one or more steering angle sensors, and/or the like) tracking operator input by an operator of the vehicle 110.

In some embodiments, the portable device 105 (and/or the remote server 175, or the like) might analyze at least one of the monitored wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle or a combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised. According to some embodiments, analyzing the combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data might comprise analyzing, with the portable device (and/or with the remote computing system), the one or more vehicle sensor data and the one or more operator input sensor data to determine whether the one or more vehicle sensor data indicates operational conditions of the vehicle that are inconsistent with the corresponding one or more operator input sensor data (which might be due to system failures or errors over time or due to accident or the like, or might be due to malicious activity by a third party (e.g., a hacker or the like)). Further analyzing the monitored wireless communications might help to determine whether any inconsistencies between the operator input and the operational conditions of the vehicle are due to maintenance-related issues or due to malicious activity by a third party (e.g., a hacker or the like).

Based on a determination that vehicle operation has been compromised, the portable device 105 (and/or the remote server, or the like) might alert the operator of the vehicle regarding the vehicle operation being compromised, using the portable device via a user interface. According to some embodiments, the user interface might be embodied within (or on an exterior surface) of the portable device 105 (such as the one or more buttons (either soft/virtual buttons or physical buttons, or the like), switches, toggles, display devices, key pads, or the other input/output devices, or the like), might be embodied within a user interface device that is part of the vehicle (e.g., a dash-mounted display device, a speaker system of the vehicle, the instrument cluster, a heads-up display, and/or the like), and/or might be embodied within at least one user device (including, but not limited to, a laptop computer, a tablet computer, a smart phone, a mobile phone, a portable gaming device, and/or the like) that is associated with the operator (or associated with a passenger of) the vehicle (see, e.g., the embodiment of FIG. 7 or the like), and/or the like. The portable device 105 (and/or the remote server, or the like) might subsequently initiate one or more remediation operations (such as the remediation operations as shown and described in detail with respect to FIG. 5 , or the like).

In some cases, the portable device 105 might be configured to set up the wireless transceiver 145 so that any wireless communications to/from any external devices via the wireless transceiver 145 must first be routed through the portable device 105. This allows for sensitive or private information regarding the functioning of the vehicle to be encrypted or prevented from being transmitted to non-authorized external devices, while allowing for detection and blocking of any computer viruses, intrusion attempts, and/or other malicious software (“malware”) sent by external devices, via the wireless transceiver, to at least one of the one or more vehicle computing systems 125, the one or more vehicular sensors 130, and/or the one or more vehicle operational systems 135. The portable device might also perform firmware validation for the firmware of the at least one of the one or more vehicle computing systems 125, the one or more vehicular sensors 130, and/or the one or more vehicle operational systems 135. In some cases, the portable device might also provide custom routing functionality for communications routes amongst the two or more of the one or more vehicle computing systems 125, the one or more vehicular sensors 130, and/or the one or more vehicle operational systems 135. These and other functionalities are described in detail with respect to FIGS. 5 and 7 .

FIG. 2 is a schematic diagram illustrating the portable device of the system of FIG. 1 in the context of a system 200 for implementing added services for OBD2 connection for IoT-capable vehicles, in accordance with various embodiments. In the embodiment of FIG. 2 , system 200 might comprise portable device 105 (which might correspond to the portable device 105 of system 100 of FIG. 1 , or the like), vehicle 110 (which might correspond to the vehicle 110 of system 100 of FIG. 1 , or the like), one or more third party devices 150 and associated databases 155 (which might correspond to the one or more third party devices 150 and associated databases 155 of system 100 of FIG. 1 , or the like), one or more networks 160 (which might correspond to network(s) 160 of system 100 of FIG. 1 , or the like), one or more networks 170 (which might correspond to service provider network(s) 170 of system 100 of FIG. 1 , or the like), remote server 175 and associated database(s) 180 (which might correspond to the remote server 175 and associated data lake 180 of system 100 of FIG. 1 , or the like), and/or the like.

Merely by way of example, according to some embodiments, the portable device 105, which in some cases might be embodied as an OBD2 dongle or the like—might include, but is not limited to, at least one processor 205, a local data storage device or data store 210, an OBD2 DLC 215 (also referred to as “OBD2 connector 215”), one or more communications transceivers 220, one or more buttons (optional) (including, without limitation, a block-wireless-communications button 225, a restore button 230, a power button (not shown), a scan button (not shown), and/or the like), one or more LED/display devices 235 (optional) (e.g., non-touchscreen display, touchscreen display, etc.), one or more other input/output (“I/O”) devices 240 (optional) (e.g., switches, toggles, key pads, microphone or other voice input, speakers, etc.), and/or the like. A vehicle operator 245 (e.g., a driver of the vehicle) might interact with the portable device 105 by interacting with at least one of the one or more buttons, the LED/display devices 235, and/or the other I/O device 240, e.g., by pressing (or depressing or making contact with) the (virtual or physical) buttons, the touchscreen display 235, the key pads, switches, toggles, etc., by looking at the display device 235 (whether non-touchscreen or touchscreen), by talking into the microphone, by listening to the speaker outputs, and/or the like. The vehicle operator 245 might also interact with the portable device 105 by plugging (or inserting) the portable device 105 into the OBD2 DLC port 115 of the vehicle 110 or by unplugging (or removing) the portable device 105 from the OBD2 DLC port 115 of the vehicle 110.

The vehicle 110 might comprise the OBD2 DLC port 115, a wireless transceiver 145 (optional), and one or more vehicle systems 250. The one or more vehicle systems 250 might include, but are not limited to, one or more vehicle computing systems (which might correspond to the one or more vehicle computing systems 125 of FIG. 1 ), one or more vehicular sensors (which might correspond to the one or more vehicular sensors 130 of FIG. 1 ), and one or more vehicle operational systems (which might correspond to the one or more vehicle operational systems 135 of FIG. 1 ), and/or the like.

The communications transceivers 220 might communicatively couple with at least one of the wireless transceiver 145 (optional), at least one third party device 150 of the one or more third party devices 150 (via network(s) 160), the remote server 175 (via network(s) 170), any user devices associated with the vehicle operator 245 or one of the passengers (shown in FIG. 7 as user devices 705 or the like), and/or the like, as depicted in FIG. 2 by the solid lines between the communications transceivers 220 and each of the networks 160 and 170 and by the lightning bolt symbols. The wireless transceiver 145 might, in some cases, also communicatively couple with at least one third party device 150 of the one or more third party devices 150 (either directly or via network(s) 160). Although lightning bolt symbols are used to denote wireless communications between the portable device 105 and each of the wireless transceiver 145 (optional), the one or more third party devices 150, the network(s) 160, the remote server 175, and the network(s) 170, and between the wireless transceiver 145 and each of the third party devices 150 and the network(s) 160, the various embodiments are not so limited, and wired as well as wireless communications may be used.

The portable device 105, vehicle 110, the OBD2 DLC port 115, the OBD2 connector 120, the (optional) wireless transceiver 145, vehicle systems 250 (which comprises the one or more vehicle computing systems, the one or more vehicular sensors, and the one or more vehicle operational systems), the one or more third party devices 150, the one or more databases 155, the network(s) 160, the network(s) 170, the remote server 175, the one or more databases 180, of system 200 FIG. 2 might otherwise be similar, if not identical, to portable device 105, the vehicle 110, the OBD2 DLC port 115, the OBD2 connector 120, the (optional) wireless transceiver 145, vehicle systems (which comprises the one or more vehicle computing systems 125, the one or more vehicular sensors 130, and the one or more vehicle operational systems 135), the one or more third party devices 150, the one or more databases 155, the network(s) 160, the service provider network(s) 170, the remote server 175, the data lake 180, respectively, of system 100 of FIG. 1 , and the descriptions of these components of system 100 are applicable to the corresponding components of system 200 of FIG. 2 , respectively.

FIG. 3 is a block diagram illustrating the various components of the vehicle 110 of the system of FIG. 1 in the context of implementing added services for OBD2 connection for IoT-capable vehicles, in accordance with various embodiments. In FIG. 3 , the blocks having dash-long dash borders represent optional blocks.

In the non-limiting example of FIG. 3 , the vehicle 110 might comprise the OBD2 DLC port 115, the controller area network (“CAN”) bus 140, and the (optional) wireless transceiver 145, as described above with respect to FIGS. 1 and 2 . CAN bus 140 might communicatively couple the OBD2 DLC port 115 and the (optional) wireless transceiver 145 with each of the vehicle systems 250 (of FIG. 2 ), which might comprise one or more vehicle computing systems 305 (which corresponds to one or more vehicle computing systems 125 of FIG. 1 ), one or more vehicular sensors 310 (which corresponds to the one or more vehicular sensors 130 of FIG. 1 ), and one or more vehicle operational systems 315 (which corresponds to the one or more vehicle operational systems 135 of FIG. 1 ), and/or the like.

In FIG. 3 , according to some embodiments, the one or more vehicle computing systems 305 might include, without limitation, at least one of an electronic throttle control (“ETC”) system 305 a, an electronic control unit (“ECU”) or an electronic control module (“ECM”) 305 b, an electronic stability control (“ESC”) system 305 c, a variable-assist power steering system 305 d, an automatic steering system 305 e, a vehicle brake system or an anti-lock braking system (“ABS”) 305 f, a vehicular computing node 305 g, or other computing systems 305 h, and/or the like. The other computing systems 305 h might, in some instances, include, but are not limited to, a collision detection/avoidance system, a navigation system, and/or the like.

In some embodiments, the one or more vehicular sensors 310 (which are depicted in FIG. 3 as rounded rectangular blocks) might include, but are not limited to, at least one of two or more accelerator pedal position sensors 310 a, one or more air-fuel mixture sensors 310 b, one or more engine air flow sensors 310 c, one or more engine speed sensors 310 d, one or more vehicle traction sensors 310 e, one or more vehicle stability sensors 310 f, one or more vehicle body motion sensors 310 g, one or more steering angle sensors 310 h, one or more vehicle speed sensors 310 i, one or more cruise control switch sensors 310 j, one or more brake actuator sensors 310 k, two or more brake pedal position sensors 310 l, or one or more other sensors 310 m, and/or the like. The one or more other sensors 310 m, in some instances, might include, without limitation, an engine temperature sensor, a fuel level sensor, one or more proximity sensors (e.g., vehicle camera-based collision avoidance system, the vehicle radar-based proximity detection system, the vehicle lidar-based proximity detection system, the vehicle sonar-based proximity detection system, etc.), one or more tire diagnostic sensors (e.g., tire-pressure sensors, tire thread sensors, tire temperature sensors, tire slip sensors, etc.), one or more other temperature sensors (e.g., heat sensors, infrared sensors, thermometers, etc.), one or more light sensors (e.g., ambient light sensors, luminosity sensors, illuminance sensors, solar light sensors, etc.), one or more cameras, one or more location sensors (e.g., global positioning system (“GPS”) devices, global navigation satellite system (“GNSS”) devices, other location sensors, etc.), one or more air quality sensors, one or more carbon monoxide sensors, one or more smoke detectors, one or more contact sensors (e.g., for the door lock system, the hood ajar detector, the trunk ajar detector, the moon/sky light ajar detector, the window open detector, and/or the like), one or more audio sensors, one or more accelerometers, one or more telecommunications signal sensors, one or more fluid leak detectors, one or more occupant sensors, one or more impact sensors, or one or more suspension system diagnostic sensors, and/or the like.

According to some embodiments, the one or more vehicle operational systems 315 might include, without limitation, at least one of an engine 315 a, an electronic throttle body (“ETB”) 315 b (which comprises an electric motor or the like), a throttle valve 315 c (which controls the amount of air going into the engine 315 a, and is controlled by the ETB 315 b), an accelerator pedal 315 d, a steering wheel 315 e, one or more brakes 315 f, a brake pedal 315 g, or other operational systems 315 h, and/or the like. In some cases, the other operational systems 315 h might include, but are not limited to, a navigation display device system, a vehicle (analog or digital) instrument gauge cluster, a vehicle heads-up-display (“HUD”) system, and/or the like.

As shown in FIG. 3 , ETC 305 a, which comprises or controls the ECM 305 b, might receive data from the two or more accelerator pedal position sensors 310 a (which detect the position of the accelerator pedal 315 d in response to the operator stepping on or releasing the accelerator pedal 315 d) and might send instructions to the ECM 305 b to control the ETB 315 b to open or close throttle valve 315 c by a calculated or predetermined amount based in part on the accelerator pedal position (and in some cases, based in part on cruise control settings data from the cruise control sensors 310 j, which track cruise control settings inputs by the operator). In some cases, the ECM 305 b might also control the ETB 315 b based in part on the engine speed (as measured by the engine speed sensor 310 d) and based in part on the vehicle speed (as measured by the vehicle speed sensor 310 i), and/or the like. The throttle valve 315 c controls the amount of air going into the engine 315 a, which controls the combustion in the engine. The engine speed, air flow, and fuel mixture in the engine 315 a can be measured by the one or more air-fuel mixture sensors 310 b, the one or more engine air flow sensors 310 c, and the one or more engine speed sensors 310 d, respectively, or the like. Such data may also be used by the ETC 305 a to control the operation of the engine 315.

According to some embodiments, the steering angle sensors 310 h might track the angle of rotation and speed of rotation of the steering wheel 315 e while the operator is steering. The variable power assist system 305 d uses this input to turn the (front) tires of the vehicle (or to otherwise turn the vehicle or change direction of travel of the vehicle, or the like). In some cases, the electronic stability control system 305 c might utilize the steering angle information in conjunction with data from one or more of the traction sensors 310 e, the stability sensors 310 f, and/or the body motion sensors 310 g to adjust the amount by which the variable power assist system 305 d turns the vehicle, so as to prevent loss of control of the vehicle, roll-overs, or the like. In some embodiments, an automatic steering system 305 e (optional) might provide corrective steering to avoid collisions or other obstacles despite operator error, or might provide autonomous driving functionality (or actual “auto pilot” functionality). The brake system or ABS 305 f might receive data from the two or more brake pedal position sensors 310 l (which detect the position of the brake pedal 315 g in response to the operator stepping on or releasing the brake pedal 315 g) and might send instructions to the brakes 315 f apply braking pressure on some or all of the tires of the vehicle 110 by a calculated amount or predetermined amount based at least in part on the brake pedal position (and in some cases, by the cruise control sensors 310 j, which track cruise control settings inputs by the operator), so as to slow down or stop the motion of the vehicle 110. The brake actuator sensors 310 k detect the effectiveness of the brakes 315 f (and might alert the operator if the brake efficiency is declining, such as due to worn brake pads, worn or damaged brake discs, or worn or damaged other brake components, or the like). The vehicle speed sensors 310 i provide vehicle speed information to at least one of the ETC 305 a, the electronic stability control system 305 c, the auto steering system 305 e, the ABS 305 f, the computing node 305 g, and/or the like.

Due to the electronic connection, rather than a mechanical linkage, between the control systems of the vehicle (e.g., accelerator pedal 315 c, brake pedal 315 f, steering wheel 315 d, and/or the like) and the corresponding operational systems of the vehicle (e.g., engine 315 a or throttle valve 315 b, brakes 315 e, variable power assist system 305 e, and/or the like), and due to potential security issues that exist with wireless communications with which modern vehicles are now equipped, third parties (e.g., hackers or the like) might be able to either control the operation of the vehicle from afar (i.e., remotely) by hacking into the vehicle computing system, the vehicular sensors, and/or the operational systems via the wireless communications system of the vehicle. In some cases, such third parties (or hackers, etc.) might send computer viruses or other malware to infect the vehicle computing system, the vehicular sensors, and/or the operational systems via the wireless communications system of the vehicle.

The various embodiments herein (as described in detail above with respect to FIG. 1 and below with respect to FIG. 5 ) provide solutions: to prevent infection of the vehicle computing system, the vehicular sensors, and/or the operational systems by viruses or other malware; to prevent intrusion attempts by third parties (or hackers, etc.) to remotely control the vehicle; to detect and remove any viruses or other malware that have already infected the vehicle computing system, the vehicular sensors, and/or the operational systems; to restore settings and configurations of the vehicle computing system, the vehicular sensors, and/or the operational systems to previous (uninfected, optimal, or operational) settings and configurations in the case that the viruses, other malware, or intrusion attempts have detrimentally changed or affected the settings and configurations of the vehicle computing system, the vehicular sensors, and/or the operational systems. The various embodiments, in some cases, might also provide encryption functionalities to protect sensor data, control data, or other data used by the various vehicle systems; provide firmware validation functionalities for the firmware of the vehicle computing system, the vehicular sensors, and/or the operational systems; provide custom routing functionality for communications routes amongst the vehicle computing system, the vehicular sensors, and/or the operational systems; and/or the like. These and other functionalities are described in detail with respect to FIGS. 1, 2, 5, and 7 .

The vehicle 110, the OBD2 DLC port 115, the CAN bus 140, the (optional) wireless transceiver 145, the one or more vehicle computing systems 305, one or more vehicular sensors 310, and the one or more vehicle operational systems 315 of FIG. 3 are otherwise similar, if not identical, to the vehicle 110, the OBD2 DLC port 115, the CAN bus 140, the (optional) wireless transceiver 145, the one or more vehicle computing systems 125, one or more vehicular sensors 130, and the one or more vehicle operational systems 135, respectively, of system 100 of FIG. 1 , and the descriptions of these components of system 100 are applicable to the corresponding components of FIG. 3 , respectively.

FIG. 4 is a schematic diagram illustrating the various components of the vehicle 110 of the system of FIG. 1 in the context of implementing added services for OBD2 connection for IoT-capable vehicles, in accordance with various embodiments. Herein, the dash-lined modules representing the various vehicle components described below denote that the particular vehicle components are at or below the surface of the body of the vehicle 110. For purposes of illustration only, the various vehicle components are depicted in approximate relative positions with respect to other vehicle components (although some vehicle components are shown as block modules whose depicted sizes would be different in the actual components and whose depicted relative positions would also differ when actually installed in the vehicle). Although certain vehicle components are shown in particular relative positions within the vehicle 110, such vehicle components need not be located in the particular relative positions as shown, and can be positioned in any portion of the vehicle as the designers/manufacturers of the vehicle deem appropriate.

In the embodiment of FIG. 4 , the vehicle 110 might comprise OBD2 DLC port 405, with which a portable device 410 (which might correspond to portable devices 105 of FIGS. 1 and 2 , or the like) might physically couple or connect. The vehicle 110 might further comprise one or more vehicle computing systems 415 (which corresponds to one or more vehicle computing systems 125 of FIG. 1 ), one or more vehicular sensors 420 (which corresponds to the one or more vehicular sensors 130 of FIG. 1 ), and one or more vehicle operational systems 425 (which corresponds to the one or more vehicle operational systems 135 of FIG. 1 ), and/or the like. In some cases, the vehicle 110 might further comprise a wireless transceiver 430 (optional) (which might correspond to wireless transceiver 145 of FIGS. 1-3 , or the like).

In FIG. 3 , according to some embodiments, the one or more vehicle computing systems 415 might include, without limitation, at least one of an electronic throttle control (“ETC”) system 415 a, an electronic control unit (“ECU”) or an electronic control module (“ECM”) 415 b, an electronic stability control (“ESC”) system 415 c, a variable-assist power steering system 415 d, an automatic steering system 415 e, a vehicle brake system or an anti-lock braking system (“ABS”) 415 f, a vehicular computing node 415 g, or other computing systems 415 h, and/or the like. The other computing systems 415 h might, in some instances, include, but are not limited to, a collision detection/avoidance system, a navigation system, and/or the like.

In some embodiments, the one or more vehicular sensors 420 might include, but are not limited to, at least one of two or more accelerator pedal position sensors 420 a, one or more air-fuel mixture sensors 420 b, one or more engine air flow sensors 420 c, one or more engine speed sensors 420 d, one or more vehicle traction sensors 420 e, one or more vehicle stability sensors 420 f, one or more vehicle body motion sensors 420 g, one or more steering angle sensors 420 h, one or more vehicle speed sensors 420 i, one or more cruise control switch sensors 420 j, one or more brake actuator sensors 420 k, two or more brake pedal position sensors 420 l, or one or more other sensors 420 m, and/or the like. The one or more other sensors 420 m, in some instances, might include, without limitation, an engine temperature sensor, a fuel level sensor, one or more proximity sensors (e.g., vehicle camera-based collision avoidance system, the vehicle radar-based proximity detection system, the vehicle lidar-based proximity detection system, the vehicle sonar-based proximity detection system, etc.), one or more tire diagnostic sensors (e.g., tire-pressure sensors, tire thread sensors, tire temperature sensors, tire slip sensors, etc.), one or more other temperature sensors (e.g., heat sensors, infrared sensors, thermometers, etc.), one or more light sensors (e.g., ambient light sensors, luminosity sensors, illuminance sensors, solar light sensors, etc.), one or more cameras, one or more location sensors (e.g., global positioning system (“GPS”) devices, global navigation satellite system (“GNSS”) devices, other location sensors, etc.), one or more air quality sensors, one or more carbon monoxide sensors, one or more smoke detectors, one or more contact sensors (e.g., for the door lock system, the hood ajar detector, the trunk ajar detector, the moon/sky light ajar detector, the window open detector, and/or the like), one or more audio sensors, one or more accelerometers, one or more telecommunications signal sensors, one or more fluid leak detectors, one or more occupant sensors, one or more impact sensors, or one or more suspension system diagnostic sensors, and/or the like.

According to some embodiments, the one or more vehicle operational systems 425 might include, without limitation, at least one of an engine 425 a, an electronic throttle body (“ETB”) 425 b (which comprises an electric motor or the like), a throttle valve 425 c (which controls the amount of air going into the engine 425 a, and is controlled by the ETB 425 b), an accelerator pedal 425 d, a steering wheel 425 e, one or more brakes 425 f, a brake pedal 425 g, or other operational systems 425 h, and/or the like. In some cases, the other operational systems 425 h might include, but are not limited to, a navigation display device system, a vehicle (analog or digital) instrument gauge cluster, a vehicle heads-up-display (“HUD”) system, and/or the like.

The vehicle 110, the OBD2 DLC port 405, the (optional) wireless transceiver 430, the one or more vehicle computing systems 415 (including, without limitation, the ETC system 415 a, the ECU or the ECM 415 b, the ESC system 415 c, the variable-assist power steering system 415 d, the automatic steering system 415 e, the vehicle brake system or the ABS 415 f, the vehicular computing node 415 g, or the other computing systems 415 h, and/or the like), one or more vehicular sensors 420 (including, but not limited to, the two or more accelerator pedal position sensors 420 a, the one or more air-fuel mixture sensors 420 b, the one or more engine air flow sensors 420 c, the one or more engine speed sensors 420 d, the one or more vehicle traction sensors 420 e, the one or more vehicle stability sensors 420 f, the one or more vehicle body motion sensors 420 g, the one or more steering angle sensors 420 h, the one or more vehicle speed sensors 420 i, the one or more cruise control switch sensors 420 j, the one or more brake actuator sensors 420 k, the two or more brake pedal position sensors 420 l, or the one or more other sensors 420 m, and/or the like), and the one or more vehicle operational systems 425 (including, without limitation, the engine 425 a, the ETB 425 b, the throttle valve 425 c, the accelerator pedal 425 d, the steering wheel 425 e, the one or more brakes 425 f, the brake pedal 425 g, or the other operational systems 425 h, and/or the like) of FIG. 4 might otherwise be similar, if not identical, to the vehicle 110, the OBD2 DLC port 115, the CAN bus 140, the (optional) wireless transceiver 145, the one or more vehicle computing systems 305 (including, without limitation, the ETC system 305 a, the ECU or the ECM 305 b, the ESC system 305 c, the variable-assist power steering system 305 d, the automatic steering system 305 e, the vehicle brake system or the ABS 305 f, the vehicular computing node 305 g, or the other computing systems 305 h, and/or the like), one or more vehicular sensors 310 (including, but not limited to, the two or more accelerator pedal position sensors 310 a, the one or more air-fuel mixture sensors 310 b, the one or more engine air flow sensors 310 c, the one or more engine speed sensors 310 d, the one or more vehicle traction sensors 310 e, the one or more vehicle stability sensors 310 f, the one or more vehicle body motion sensors 310 g, the one or more steering angle sensors 310 h, the one or more vehicle speed sensors 310 i, the one or more cruise control switch sensors 310 j, the one or more brake actuator sensors 310 k, the two or more brake pedal position sensors 310 l, or the one or more other sensors 310 m, and/or the like), and the one or more vehicle operational systems 315 (including, without limitation, the engine 315 a, the ETB 315 b, the throttle valve 315 c, the accelerator pedal 315 d, the steering wheel 315 e, the one or more brakes 315 f, the brake pedal 315 g, or the other operational systems 315 h, and/or the like), respectively, of FIG. 3 , and the descriptions of these components of FIG. 3 are applicable to the corresponding components of FIG. 4 , respectively. The portable device 410 of FIG. 4 might otherwise be similar, if not identical, to the portable device 105 of system 100 of FIG. 1 or system 200 of FIG. 2 , and the descriptions of the portable device 105 of FIGS. 1 and 2 are applicable to the portable device of FIG. 4 .

FIGS. 5A-5C (collectively, “FIG. 5 ”) are flow diagrams illustrating a method 500 for implementing added services for OBD2 connection for IoT-capable vehicles, in accordance with various embodiments.

While the techniques and procedures are depicted and/or described in a certain order for purposes of illustration, it should be appreciated that certain procedures may be reordered and/or omitted within the scope of various embodiments. Moreover, while the method 500 illustrated by FIG. 5 can be implemented by or with (and, in some cases, are described below with respect to) the systems 100 and 200 of FIGS. 1 and 2 , respectively (or components thereof), as well as vehicle 110 (or components thereof) of FIGS. 3 and 4 , such methods may also be implemented using any suitable hardware (or software) implementation. Similarly, while each of the systems 100 and 200 of FIGS. 1 and 2 , respectively (or components thereof), as well as vehicle 110 (or components thereof) of FIGS. 3 and 4 , can operate according to the method 500 or 500′ illustrated by FIG. 5 (e.g., by executing instructions embodied on a computer readable medium), the systems 100 and 200 of FIGS. 1 and 2 , as well as vehicle 110 of FIGS. 3 and 4 can each also operate according to other modes of operation and/or perform other suitable procedures.

In the non-limiting embodiment of FIG. 5A, method 500 might comprise, at block 505, monitoring, with a portable device (which might correspond to portable devices 105 and 410 of FIGS. 1, 2, and 4 , or the like) in communication with one or more computing systems of a vehicle (which might correspond to vehicle 110 of FIGS. 1-4 , or the like) via an on-board diagnostics (“OBD2”) data link connector (“DLC”) port (which might correspond to OBD2 DLC port 115 and 405 of FIGS. 1-4 , or the like), wireless communications between at least one vehicle computing system of the one or more computing systems of the vehicle and at least one device external to the vehicle. In some cases, the one or more computing systems (which might correspond to vehicle computing systems 125, 305 a-305 i, and 415 a-415 i of FIGS. 1, 3, and 4 , or the like) of the vehicle might include, without limitation, at least one of an electronic control unit (“ECU”), an electronic control module (“ECM”), an electronic throttle control (“ETC”) system, an electronic stability control (“ESC”) system, a variable-assist power steering system, an automatic steering system, an anti-lock braking system (“ABS”), or a vehicular computing node, and/or the like.

Method 500 might further comprise monitoring, with the portable device via the OBD2 DLC port, one or more vehicle sensor data from one or more vehicular sensors tracking operational conditions of the vehicle (block 510) and monitoring, with the portable device via the OBD2 DLC port, one or more operator input sensor data from one or more operator input sensors tracking operator input by an operator of the vehicle (block 515). In some cases, the one or more vehicular sensors tracking operational conditions of the vehicle might include, but are not limited to, at least one of one or more engine speed sensors, one or more engine air flow sensors, one or more air-fuel mixture sensors, one or more vehicle speed sensors, one or more brake actuator sensors, one or more vehicle traction sensors, one or more vehicle stability sensors, one or more vehicle body motion sensors, and/or the like. The one or more operator input sensors tracking operator input by the operator of the vehicle might include, without limitation, at least one of one or more accelerator pedal position sensors, one or more cruise control switch sensors, one or more brake pedal position sensors, one or more steering angle sensors, and/or the like.

At block 520, method 500 might comprise analyzing, with the portable device (and/or with at least one remote computing system, such as remote server 175 in FIGS. 1 and 2 , or the like), at least one of the monitored wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle or a combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised. In some cases, analyzing the combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data might comprise analyzing, with the portable device (and/or with the at least one remote computing system), the one or more vehicle sensor data and the one or more operator input sensor data to determine whether the one or more vehicle sensor data indicates operational conditions of the vehicle that are inconsistent with the corresponding one or more operator input sensor data (block 525).

Method 500, in some embodiments, might comprise encrypting, with the portable device (and/or with the at least one remote computing system), the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data (block 530) and storing, with the portable device, the encrypted one or more vehicle sensor data and the encrypted one or more operator input sensor data in a local data storage device of the portable device (block 535) or storing, with the at least one remote computing system, the encrypted one or more vehicle sensor data and the encrypted one or more operator input sensor data in a remote data store (such as data lake 180 of FIG. 1 , or the like). In some cases, encrypting the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data might include using one or more cryptographic protocols or techniques comprising AES symmetric-key algorithm, Diffie-Hellman key exchange, SHA-1 hash function, forward secrecy, deniable authentication, or malleable encryption, and/or the like. Although FIG. 5A depicts the encryption and storing operations (of block 530 and 535) as being performed after the analysis operation (of blocks 520 and 525), the various embodiments are not so limited, and encrypting and storing the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data can be performed either before or after analyzing the at least one of the monitored wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle or the combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised. The latter is as shown in FIG. 5A, while the former requires retrieval and decryption of the at least one of the monitored wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle or the combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data prior to analysis.

At block 540, method 500 might comprise, based on a determination that vehicle operation has been compromised, alerting the operator of the vehicle regarding the vehicle operation being compromised, using the portable device via a user interface. According to some embodiments, the user interface might be embodied within (or on an exterior surface) of the portable device (such as the buttons 225 and 230, the display devices 235, or the other input/output devices 240 of system 200 of FIG. 2 , or the like), might be embodied within a user interface device that is part of the vehicle (e.g., a dash-mounted display device, a speaker system of the vehicle, the instrument cluster, a heads-up display, and/or the like), and/or might be embodied within at least one user device (including, but not limited to, a laptop computer, a tablet computer, a smart phone, a mobile phone, a portable gaming device, and/or the like) that is associated with the operator (or a passenger of) the vehicle (see, e.g., the embodiment of FIG. 7 or the like), and/or the like. Method 500, at block 545 might further comprise initiating, with the portable device, one or more remediation operations (embodiments of which are shown and described with respect to FIG. 5B).

In FIG. 5B, for the embodiments corresponding to the processes at blocks 550 and 555, the vehicle might be an Internet of Things (“IoT”)-capable vehicle and the at least one device external to the vehicle might comprise at least one IoT-capable device. The wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle might comprise machine-to-machine IoT communications. For the embodiments corresponding to the processes at blocks 560 and 565, the wireless communications might be either machine-to-machine IoT communications or other (non-IoT) types of wireless communications, or the like

With reference to FIG. 5B, initiating the one or more remediation operations (at block 545) might comprise, at block 550, disrupting, with the portable device, communication between the at least one vehicle computing system and the at least one device external to the vehicle, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the machine-to-machine IoT communications (in cases in which the portable device is an IoT gateway through which all IoT communications pass) and based on the operator action comprising disconnecting the portable device from the OBD2 DLC port. In other words, when the user disconnects the portable device from the OBD2 DLC port, because it had become the point or gateway through which all IoT communications pass, the portable device physically disrupts the communication between the at least one vehicle computing system and the at least one device external to the vehicle. The process might proceed to block 595 in FIG. 5D, following the circular marker denoted, “B,” at which method 500 might further comprise, in response to the operator reconnecting the portable device into the OBD2 DLC port, establishing, with the portable device, communication between the at least one vehicle computing system and one or more telematics sources (block 595).

Turning back to FIG. 5B, initiating the one or more remediation operations (at block 545) might comprise, at block 555, disrupting, with the portable device, communication between the at least one vehicle computing system and the at least one device external to the vehicle, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the machine-to-machine IoT communications (in cases in which the portable device is an IoT gateway through which all IoT communications pass) and based on the operator action comprising depressing the block-wireless-communications button on the portable device (which might correspond to the block-wireless-communications button 225 of FIG. 2 , or the like). In other words, when the user presses (or depresses) the block-wireless-communications button on the portable device, because it had become the point or gateway through which all IoT communications pass, the portable device logically (or physically via an internal physical switch) disrupts the communication between the at least one vehicle computing system and the at least one device external to the vehicle.

Alternatively, either in cases in which the portable device is an IoT gateway through which all IoT communications pass or in cases in which other wireless devices have access to the vehicle computing systems (and/or other vehicle systems) (i.e., where wireless communications can bypass the portable device), initiating the one or more remediation operations (at block 545) might comprise, at block 555, disrupting, with the portable device, communication between the at least one vehicle computing system and the at least one device external to the vehicle by jamming all wireless communications within at least one set of telecommunications frequency ranges to and from the vehicle, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the wireless communications and based on the operator action comprising depressing the block-wireless-communications button on the portable device. In some cases, the portable device might selectively jam only certain ranges of wireless communications frequencies within the vehicle (or within a short distance from the portable device, e.g., distance sufficient to jam any wireless device on any portion of the vehicle from front to rear bumper, from roof to undercarriage (and tire), without significantly or unreasonable jamming wireless communications for other vehicles or nearby buildings, or the like). Alternatively, the portable device might jam all wireless communications frequencies within the vehicle (or within a short distance from the portable device, as described above). Where all wireless communications frequencies (or at least the frequencies associated with telematics sources) have been disrupted, jammed, or otherwise blocked, the vehicle would still function but would operate without telematics data to support operation (i.e., the vehicle would revert to substantially or effectively “manual” operation, with only the on-board operational systems that can function within externally sourced telematics being operational to aid the operator in the operation of the vehicle).

According to some embodiments, alternative or in addition to the processes at blocks 550-560, initiating the one or more remediation operations (at block 545) might comprise, at block 565, restoring, with the portable device, settings and configurations for at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the wireless communications and based on the operator action comprising depressing the restore button on the portable device (which might correspond to the restore button 230 of FIG. 2 , or the like). The settings and configurations for the at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors might comprise one of factory settings and configurations or previously saved settings and configurations, and/or the like. In other words, when the user presses (or depresses) the restore button on the portable device, the portable device restores the settings and configurations for the computing systems and/or the sensors to a previous set of settings and configurations. This ensures that any viruses, intrusion attempts, or other malicious software (“malware”) or the like that have infected the computing systems and/or the sensors via the wireless communications can be eliminated by restoration to a restoration point or the like. Any changed settings and configurations due to intrusion attempts by hackers or the like may also be reset by restoration to a restoration point or the like. FIG. 5C illustrates the processes for detecting, blocking, and removing any viruses, intrusion attempts, or other malware, or the like (which includes those viruses, intrusion attempts, or other malware, or the like that cannot be eliminated by restoration, etc.).

Turning back to the process at block 545 in FIG. 5A, method 500 proceeds to block 570 in FIG. 5C, following the circular marker denoted, “A.” With reference to block 570 in FIG. 5C (following circular marker, “A” in FIG. 5A), method 500 might comprise detecting, with the portable device, whether the wireless communications comprises at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software. The process at block 570 might, in some cases, be part of the process of analyzing the at least one of the monitored wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle or the combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised (at block 520). Based on detection of at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software in the wireless communications, method 500 might further comprise, at block 575, blocking, with the portable device, the at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software from infecting the at least one vehicle computing system via the wireless communications.

Method 500 might further comprise detecting, with the portable device, whether at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors comprises at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software (block 580), and (based on detection of at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software in at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors) removing, with the portable device, the at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software from the at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors (block 585).

In some cases, method 500 might comprise, at block 590, validating, with the portable device, firmware of at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors.

Exemplary System and Hardware Implementation

FIG. 6 is a block diagram illustrating an exemplary computer or system hardware architecture, in accordance with various embodiments. FIG. 6 provides a schematic illustration of one embodiment of a computer system 600 of the service provider system hardware that can perform the methods provided by various other embodiments, as described herein, and/or can perform the functions of computer or hardware system (i.e., portable devices 105 and 410, vehicle systems 250 (including, but not limited to, vehicle computing systems 125, 305 a-305 h, and 415 a-415 h, vehicular sensors 130, 310 a-310 m, and 420 a-420 m, vehicle operational systems 135, 315 a-315 h, and 425 a-425 h, etc.), third party devices 150, and remote server 175, etc.), as described above. It should be noted that FIG. 6 is meant only to provide a generalized illustration of various components, of which one or more (or none) of each may be utilized as appropriate. FIG. 6 , therefore, broadly illustrates how individual system elements may be implemented in a relatively separated or relatively more integrated manner.

The computer or hardware system 600—which might represent an embodiment of the computer or hardware system (i.e., portable devices 105 and 410, vehicle systems 250 (including, but not limited to, vehicle computing systems 125, 305 a-305 h, and 415 a-415 h, vehicular sensors 130, 310 a-310 m, and 420 a-420 m, vehicle operational systems 135, 315 a-315 h, and 425 a-425 h, etc.), third party devices 150, and remote server 175, etc.), described above with respect to FIGS. 1-4 —is shown comprising hardware elements that can be electrically coupled via a bus 605 (or may otherwise be in communication, as appropriate). The hardware elements may include one or more processors 610, including, without limitation, one or more general-purpose processors and/or one or more special-purpose processors (such as microprocessors, digital signal processing chips, graphics acceleration processors, and/or the like); one or more input devices 615, which can include, without limitation, a mouse, a keyboard, sensors, and/or the like; and one or more output devices 620, which can include, without limitation, a display device, a printer, indicator lights, and/or the like.

The computer or hardware system 600 may further include (and/or be in communication with) one or more storage devices 625, which can comprise, without limitation, local and/or network accessible storage, and/or can include, without limitation, a disk drive, a drive array, an optical storage device, solid-state storage device such as a random access memory (“RAM”) and/or a read-only memory (“ROM”), which can be programmable, flash-updateable, and/or the like. Such storage devices may be configured to implement any appropriate data stores, including, without limitation, various file systems, database structures, and/or the like.

The computer or hardware system 600 might also include a communications subsystem 630, which can include, without limitation, a modem, a network card (wireless or wired), an infra-red communication device, a wireless communication device and/or chipset (such as a Bluetooth™ device, an 802.11 device, a WiFi device, a WiMax device, a WWAN device, cellular communication facilities, etc.), and/or the like. The communications subsystem 630 may permit data to be exchanged with a network (such as the network described below, to name one example), with other computer or hardware systems, and/or with any other devices described herein. In many embodiments, the computer or hardware system 600 will further comprise a working memory 635, which can include a RAM or ROM device, as described above.

The computer or hardware system 600 also may comprise software elements, shown as being currently located within the working memory 635, including an operating system 640, device drivers, executable libraries, and/or other code, such as one or more application programs 645, which may comprise computer programs provided by various embodiments (including, without limitation, hypervisors, VMs, and the like), and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein. Merely by way of example, one or more procedures described with respect to the method(s) discussed above might be implemented as code and/or instructions executable by a computer (and/or a processor within a computer); in an aspect, then, such code and/or instructions can be used to configure and/or adapt a general purpose computer (or other device) to perform one or more operations in accordance with the described methods.

A set of these instructions and/or code might be encoded and/or stored on a non-transitory computer readable storage medium, such as the storage device(s) 625 described above. In some cases, the storage medium might be incorporated within a computer system, such as the system 600. In other embodiments, the storage medium might be separate from a computer system (i.e., a removable medium, such as a compact disc, etc.), and/or provided in an installation package, such that the storage medium can be used to program, configure, and/or adapt a general purpose computer with the instructions/code stored thereon. These instructions might take the form of executable code, which is executable by the computer or hardware system 600 and/or might take the form of source and/or installable code, which, upon compilation and/or installation on the computer or hardware system 600 (e.g., using any of a variety of generally available compilers, installation programs, compression/decompression utilities, etc.) then takes the form of executable code.

It will be apparent to those skilled in the art that substantial variations may be made in accordance with specific requirements. For example, customized hardware (such as programmable logic controllers, field-programmable gate arrays, application-specific integrated circuits, and/or the like) might also be used, and/or particular elements might be implemented in hardware, software (including portable software, such as applets, apps, etc.), or both. Further, connection to other computing devices such as network input/output devices may be employed.

As mentioned above, in one aspect, some embodiments may employ a computer or hardware system (such as the computer or hardware system 600) to perform methods in accordance with various embodiments of the invention. According to a set of embodiments, some or all of the procedures of such methods are performed by the computer or hardware system 600 in response to processor 610 executing one or more sequences of one or more instructions (which might be incorporated into the operating system 640 and/or other code, such as an application program 645) contained in the working memory 635. Such instructions may be read into the working memory 635 from another computer readable medium, such as one or more of the storage device(s) 625. Merely by way of example, execution of the sequences of instructions contained in the working memory 635 might cause the processor(s) 610 to perform one or more procedures of the methods described herein.

The terms “machine readable medium” and “computer readable medium,” as used herein, refer to any medium that participates in providing data that causes a machine to operate in a specific fashion. In an embodiment implemented using the computer or hardware system 600, various computer readable media might be involved in providing instructions/code to processor(s) 610 for execution and/or might be used to store and/or carry such instructions/code (e.g., as signals). In many implementations, a computer readable medium is a non-transitory, physical, and/or tangible storage medium. In some embodiments, a computer readable medium may take many forms, including, but not limited to, non-volatile media, volatile media, or the like. Non-volatile media includes, for example, optical and/or magnetic disks, such as the storage device(s) 625. Volatile media includes, without limitation, dynamic memory, such as the working memory 635. In some alternative embodiments, a computer readable medium may take the form of transmission media, which includes, without limitation, coaxial cables, copper wire, and fiber optics, including the wires that comprise the bus 605, as well as the various components of the communication subsystem 630 (and/or the media by which the communications subsystem 630 provides communication with other devices). In an alternative set of embodiments, transmission media can also take the form of waves (including, without limitation, radio, acoustic, and/or light waves, such as those generated during radio-wave and infra-red data communications).

Common forms of physical and/or tangible computer readable media include, for example, a floppy disk, a flexible disk, a hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, or any other medium from which a computer can read instructions and/or code.

Various forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to the processor(s) 610 for execution. Merely by way of example, the instructions may initially be carried on a magnetic disk and/or optical disc of a remote computer. A remote computer might load the instructions into its dynamic memory and send the instructions as signals over a transmission medium to be received and/or executed by the computer or hardware system 600. These signals, which might be in the form of electromagnetic signals, acoustic signals, optical signals, and/or the like, are all examples of carrier waves on which instructions can be encoded, in accordance with various embodiments of the invention.

The communications subsystem 630 (and/or components thereof) generally will receive the signals, and the bus 605 then might carry the signals (and/or the data, instructions, etc. carried by the signals) to the working memory 635, from which the processor(s) 605 retrieves and executes the instructions. The instructions received by the working memory 635 may optionally be stored on a storage device 625 either before or after execution by the processor(s) 610.

As noted above, a set of embodiments comprises methods and systems for implementing Internet of Things (“IoT”) functionality, and, in particular embodiments, to methods, systems, apparatus, and computer software for implementing added services for OBD2 connection for IoT-capable vehicles. FIG. 7 illustrates a schematic diagram of a system 700 that can be used in accordance with one set of embodiments. The system 700 can include one or more user computers, user devices, or customer devices 705. A user computer, user device, or customer device 705 can be a general purpose personal computer (including, merely by way of example, desktop computers, tablet computers, laptop computers, handheld computers, and the like, running any appropriate operating system, several of which are available from vendors such as Apple, Microsoft Corp., and the like), cloud computing devices, a server(s), and/or a workstation computer(s) running any of a variety of commercially-available UNIX™ or UNIX-like operating systems. A user computer, user device, or customer device 705 can also have any of a variety of applications, including one or more applications configured to perform methods provided by various embodiments (as described above, for example), as well as one or more office applications, database client and/or server applications, and/or web browser applications. Alternatively, a user computer, user device, or customer device 705 can be any other electronic device, such as a thin-client computer, Internet-enabled mobile telephone, smart phone, and/or personal digital assistant, capable of communicating via a network (e.g., the network(s) 710 described below) and/or of displaying and navigating web pages or other types of electronic documents. Although the exemplary system 700 is shown with two user computers, user devices, or customer devices 705, any number of user computers, user devices, or customer devices can be supported.

Certain embodiments operate in a networked environment, which can include a network(s) 710. The network(s) 710 can be any type of network familiar to those skilled in the art that can support data communications using any of a variety of commercially-available (and/or free or proprietary) protocols, including, without limitation, TCP/IP, SNA™, IPX™, AppleTalk™, and the like. Merely by way of example, the network(s) 710 (similar to networks 160 and 170 of FIGS. 1 and 2 , or the like) can each include a local area network (“LAN”), including, without limitation, a fiber network, an Ethernet network, a Token-Ring™ network, and/or the like; a wide-area network (“WAN”); a wireless wide area network (“WWAN”); a virtual network, such as a virtual private network (“VPN”); the Internet; an intranet; an extranet; a public switched telephone network (“PSTN”); an infra-red network; a wireless network, including, without limitation, a network operating under any of the IEEE 802.11 suite of protocols, the Bluetooth™ protocol known in the art, and/or any other wireless protocol; and/or any combination of these and/or other networks. In a particular embodiment, the network might include an access network of the service provider (e.g., an Internet service provider (“ISP”)). In another embodiment, the network might include a core network of the service provider, and/or the Internet.

Embodiments can also include one or more server computers 715. Each of the server computers 715 may be configured with an operating system, including, without limitation, any of those discussed above, as well as any commercially (or freely) available server operating systems. Each of the servers 715 may also be running one or more applications, which can be configured to provide services to one or more clients 705 and/or other servers 715.

Merely by way of example, one of the servers 715 might be a data server, a web server, a cloud computing device(s), or the like, as described above. The data server might include (or be in communication with) a web server, which can be used, merely by way of example, to process requests for web pages or other electronic documents from user computers 705. The web server can also run a variety of server applications, including HTTP servers, FTP servers, CGI servers, database servers, Java servers, and the like. In some embodiments of the invention, the web server may be configured to serve web pages that can be operated within a web browser on one or more of the user computers 705 to perform methods of the invention.

The server computers 715, in some embodiments, might include one or more application servers, which can be configured with one or more applications accessible by a client running on one or more of the client computers 705 and/or other servers 715. Merely by way of example, the server(s) 715 can be one or more general purpose computers capable of executing programs or scripts in response to the user computers 705 and/or other servers 715, including, without limitation, web applications (which might, in some cases, be configured to perform methods provided by various embodiments). Merely by way of example, a web application can be implemented as one or more scripts or programs written in any suitable programming language, such as Java™, C, C#™ or C++, and/or any scripting language, such as Perl, Python, or TCL, as well as combinations of any programming and/or scripting languages. The application server(s) can also include database servers, including, without limitation, those commercially available from Oracle™, Microsoft™, Sybase™, IBM™, and the like, which can process requests from clients (including, depending on the configuration, dedicated database clients, API clients, web browsers, etc.) running on a user computer, user device, or customer device 705 and/or another server 715. In some embodiments, an application server can perform one or more of the processes for implementing IoT functionality, and, in particular embodiments, to methods, systems, apparatus, and computer software for implementing added services for OBD2 connection for IoT-capable vehicles, or the like, as described in detail above. Data provided by an application server may be formatted as one or more web pages (comprising HTML, JavaScript, etc., for example) and/or may be forwarded to a user computer 705 via a web server (as described above, for example). Similarly, a web server might receive web page requests and/or input data from a user computer 705 and/or forward the web page requests and/or input data to an application server. In some cases, a web server may be integrated with an application server.

In accordance with further embodiments, one or more servers 715 can function as a file server and/or can include one or more of the files (e.g., application code, data files, etc.) necessary to implement various disclosed methods, incorporated by an application running on a user computer 705 and/or another server 715. Alternatively, as those skilled in the art will appreciate, a file server can include all necessary files, allowing such an application to be invoked remotely by a user computer, user device, or customer device 705 and/or server 715.

It should be noted that the functions described with respect to various servers herein (e.g., application server, database server, web server, file server, etc.) can be performed by a single server and/or a plurality of specialized servers, depending on implementation-specific needs and parameters.

In certain embodiments, the system can include one or more databases 720 a-720 n (collectively, “databases 720”). The location of each of the databases 720 is discretionary: merely by way of example, a database 720 a might reside on a storage medium local to (and/or resident in) a server 715 a (and/or a user computer, user device, or customer device 705). Alternatively, a database 720 n can be remote from any or all of the computers 705, 715, so long as it can be in communication (e.g., via the network 710) with one or more of these. In a particular set of embodiments, a database 720 can reside in a storage-area network (“SAN”) familiar to those skilled in the art. (Likewise, any necessary files for performing the functions attributed to the computers 705, 715 can be stored locally on the respective computer and/or remotely, as appropriate.) In one set of embodiments, the database 720 can be a relational database, such as an Oracle database, that is adapted to store, update, and retrieve data in response to SQL-formatted commands. The database might be controlled and/or maintained by a database server, as described above, for example.

According to some embodiments, system 700 might further comprise a portable device 725 (which might correspond to portable devices 105 and 410 of FIGS. 1, 2, and 4 , or the like) and an on-board diagnostics (“OBD2”) data link connector (“DLC”) port 730 (which might correspond to OBD2 DLC port 115 and 405 of FIGS. 1-4 , or the like) disposed with vehicle 735 (which might correspond to vehicle 110 of FIGS. 1-4 , or the like). The portable device 725 might comprise a corresponding OBD2 DLC 740 (which might correspond to OBD2 DLC 120 and 215 of FIGS. 1 and 2 , or the like) that is configured to removably attach or connect with the OBD2 DLC port 730. System 700 might further comprise one or more vehicle computing systems 745 (which might correspond to vehicle computing systems 125, 305 a-305 h, and 415 a-415 h of FIGS. 1, 3 , and 4, or the like), one or more vehicular sensors 750 (which might correspond to portable devices 105 and 410 of FIGS. 1, 2, and 4 , or the like), one or more vehicle operational systems 755 (which might correspond to vehicular sensors 130, 310 a-310 m, and 420 a-420 m of FIGS. 1, 3, and 4 , or the like) (collectively, “vehicle systems,” which might correspond to vehicle systems 250 of FIG. 2 , or the like), and (optionally) a wireless transceiver 760 (which might correspond to vehicle operational systems 135, 315 a-315 h, and 425 a-425 h of FIGS. 1, 3, and 4 , or the like).

In some embodiments, the one or more vehicle computing systems 745 of the vehicle 735 might include, without limitation, at least one of an electronic control unit (“ECU”), an electronic control module (“ECM”), an electronic throttle control (“ETC”) system, an electronic stability control (“ESC”) system, a variable-assist power steering system, an automatic steering system, an anti-lock braking system (“ABS”), a vehicular computing node, or other computing systems, and/or the like. The one or more vehicular sensors, in some instances, might include, but is not limited to, at least one of one or more accelerator pedal position sensors, one or more engine speed sensors, one or more engine air flow sensors, one or more air-fuel mixture sensors, one or more vehicle speed sensors, one or more cruise control switch sensors, one or more brake pedal position sensors, one or more brake actuator sensors, one or more vehicle traction sensors, one or more vehicle stability sensors, one or more vehicle body motion sensors, one or more steering angle sensors, or other sensors, and/or the like. In some cases, the one or more vehicle operational systems 755 might include, without limitation, at least one of an accelerator pedal, an engine, a throttle valve, a steering wheel, one or more brakes, a brake pedal, or other operational systems, and/or the like.

In some cases, system 700 might further comprise one or more third party devices 765 (which might correspond to third party devices 150 of FIGS. 1 and 2 , or the like), which might have a corresponding set of databased 770 (which might correspond to databases 155 of FIGS. 1 and 2 , or the like).

In operation, the portable device 725 (when connected to, or plugged into, the OBD2 DLC port 730) might monitor wireless communications between at least one vehicle computing system of the one or more vehicle computing systems 745 (or the vehicle systems collectively) and at least one third party device 765 (or other device external to the vehicle 735). The portable device 725 (when connected to, or plugged into, the OBD2 DLC port 730) might also monitor one or more vehicle sensor data from one or more vehicular sensors 750 (e.g., at least one of one or more engine speed sensors, one or more engine air flow sensors, one or more air-fuel mixture sensors, one or more vehicle speed sensors, one or more brake actuator sensors, one or more vehicle traction sensors, one or more vehicle stability sensors, one or more vehicle body motion sensors, and/or the like) tracking operational conditions of the vehicle (i.e., conditions of the one or more vehicle operational systems 755 or the like) and might also monitor one or more operator input sensor data from one or more operator input sensors 750 (e.g., at least one of one or more accelerator pedal position sensors, one or more cruise control switch sensors, one or more brake pedal position sensors, one or more steering angle sensors, and/or the like) tracking operator input by an operator of the vehicle 735.

In some embodiments, the portable device 725 (while in other embodiments, at least one of the servers 715 a or 715 b (which might correspond to remote server 175 in FIGS. 1 and 2 , or the like)) might analyze at least one of the monitored wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle or a combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised. Based on a determination that vehicle operation has been compromised, the portable device 725 (or the at least one of the servers 715 a or 715 b, or the like) might alert the operator of the vehicle regarding the vehicle operation being compromised, using the portable device via a user interface (in some cases, via at least one of user devices 705 a or 705 b, or the like). The portable device 725 (or the at least one of the servers 715 a or 715 b, or the like) might subsequently initiate one or more remediation operations (such as the remediation operations as shown and described above with respect to FIG. 5 , or the like). These and other functions of the system 700 (and its components) are described in greater detail above with respect to FIGS. 1-5 .

While certain features and aspects have been described with respect to exemplary embodiments, one skilled in the art will recognize that numerous modifications are possible. For example, the methods and processes described herein may be implemented using hardware components, software components, and/or any combination thereof. Further, while various methods and processes described herein may be described with respect to particular structural and/or functional components for ease of description, methods provided by various embodiments are not limited to any particular structural and/or functional architecture but instead can be implemented on any suitable hardware, firmware and/or software configuration. Similarly, while certain functionality is ascribed to certain system components, unless the context dictates otherwise, this functionality can be distributed among various other system components in accordance with the several embodiments.

Moreover, while the procedures of the methods and processes described herein are described in a particular order for ease of description, unless the context dictates otherwise, various procedures may be reordered, added, and/or omitted in accordance with various embodiments. Moreover, the procedures described with respect to one method or process may be incorporated within other described methods or processes; likewise, system components described according to a particular structural architecture and/or with respect to one system may be organized in alternative structural architectures and/or incorporated within other described systems. Hence, while various embodiments are described with—or without—certain features for ease of description and to illustrate exemplary aspects of those embodiments, the various components and/or features described herein with respect to a particular embodiment can be substituted, added and/or subtracted from among other described embodiments, unless the context dictates otherwise. Consequently, although several exemplary embodiments are described above, it will be appreciated that the invention is intended to cover all modifications and equivalents within the scope of the following claims. 

What is claimed is:
 1. A method, comprising: monitoring, with a portable device in communication with one or more computing systems of a vehicle via an on-board diagnostics (“OBD2”) data link connector (“DLC”) port, wireless communications between at least one vehicle computing system of the one or more computing systems of the vehicle and at least one device external to the vehicle; monitoring, with the portable device via the OBD2 DLC port, one or more vehicle sensor data from one or more vehicular sensors tracking operational conditions of the vehicle; monitoring, with the portable device via the OBD2 DLC port, one or more operator input sensor data from one or more operator input sensors tracking operator input by an operator of the vehicle; analyzing, with the portable device, at least one of the monitored wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle or a combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised; based on a determination that vehicle operation has been compromised, alerting the operator of the vehicle regarding the vehicle operation being compromised, using the portable device via a user interface; and initiating, with the portable device, one or more remediation operations, wherein the vehicle is an Internet of Things (“IoT”)-capable vehicle and the at least one device external to the vehicle comprises at least one IoT-capable device, wherein the wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle comprises machine-to-machine IoT communications, and the portable device is an IoT gateway through which all IoT communications pass, wherein initiating the one or more remediation operations comprises, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the machine-to-machine IoT communications and based on the operator action comprising disconnecting the portable device from the OBD2 DLC port, disrupting, with the portable device, communication between the at least one vehicle computing system and the at least one device external to the vehicle.
 2. The method of claim 1, wherein the one or more computing systems of the vehicle comprise at least one of an electronic control unit (“ECU”), an electronic control module (“ECM”), an electronic throttle control (“ETC”) system, an electronic stability control (“ESC”) system, a variable-assist power steering system, an automatic steering system, an anti-lock braking system (“ABS”), or a vehicular computing node.
 3. The method of claim 1, wherein the one or more vehicular sensors comprise at least one of one or more accelerator pedal position sensors, one or more engine speed sensors, one or more engine air flow sensors, one or more air-fuel mixture sensors, one or more vehicle speed sensors, one or more cruise control switch sensors, one or more brake pedal position sensors, one or more brake actuator sensors, one or more vehicle traction sensors, one or more vehicle stability sensors, one or more vehicle body motion sensors, or one or more steering angle sensors.
 4. The method of claim 1, wherein analyzing the combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data comprises analyzing, with the portable device, the one or more vehicle sensor data and the one or more operator input sensor data to determine whether the one or more vehicle sensor data indicates operational conditions of the vehicle that are inconsistent with the corresponding one or more operator input sensor data.
 5. The method of claim 1, further comprising: in response to the operator reconnecting the portable device into the OBD2 DLC port, establishing, with the portable device, communication between the at least one vehicle computing system and one or more telematics sources.
 6. The method of claim 1, wherein the portable device is an IoT gateway through which all IoT communications pass, wherein the portable device comprises a block-wireless-communications button, wherein initiating the one or more remediation operations comprises, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the machine-to-machine IoT communications and based on the operator action comprising depressing the block-wireless-communications button on the portable device, disrupting, with the portable device, communication between the at least one vehicle computing system and the at least one device external to the vehicle.
 7. The method of claim 1, wherein the portable device comprises a block-wireless-communications button, wherein initiating the one or more remediation operations comprises, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the wireless communications and based on the operator action comprising depressing the block-wireless-communications button on the portable device, disrupting, with the portable device, communication between the at least one vehicle computing system and the at least one device external to the vehicle by jamming all wireless communications within at least one set of telecommunications frequency ranges to and from the vehicle.
 8. The method of claim 1, wherein the portable device comprises a restore button, wherein initiating the one or more remediation operations comprises, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the wireless communications and based on the operator action comprising depressing the restore button on the portable device, restoring, with the portable device, settings and configurations for at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors, wherein the settings and configurations for the at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors comprise one of factory settings and configurations or previously saved settings and configurations.
 9. The method of claim 1, further comprising: encrypting, with the portable device, the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data; and storing, with the portable device, the encrypted one or more vehicle sensor data and the encrypted one or more operator input sensor data in a local data storage device of the portable device; wherein encrypting and storing the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data are performed either before or after analyzing the at least one of the monitored wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle or the combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised.
 10. The method of claim 9, wherein encrypting the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data comprises encrypting, with the portable device, the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, using one or more cryptographic protocols or techniques comprising AES symmetric-key algorithm, Diffie-Hellman key exchange, SHA-1 hash function, forward secrecy, deniable authentication, or malleable encryption.
 11. The method of claim 1, wherein analyzing the at least one of the monitored wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle or the combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised comprises detecting, with the portable device, whether the wireless communications comprises at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software and blocking, with the portable device, the at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software from infecting the at least one vehicle computing system via the wireless communications.
 12. The method of claim 1, further comprising: detecting, with the portable device, whether at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors comprises at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software; and removing, with the portable device, the at least one of one or more viruses, one or more electronic intrusion attempts, or one or more other malicious software from the at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors.
 13. The method of claim 1, further comprising: validating, with the portable device, firmware of at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors.
 14. A portable device, comprising: an on-board diagnostics (“OBD2”) data link connector (“DLC”) in communication with one or more computing systems of a vehicle via an OBD2 DLC port of the vehicle; at least one processor; a data storage device; and a non-transitory computer readable medium communicatively coupled to the at least one processor, the non-transitory computer readable medium having stored thereon computer software comprising a set of instructions that, when executed by the at least one processor, causes the portable device to: monitor, via the OBD2 DLC port, wireless communications between at least one vehicle computing system of the one or more computing systems of the vehicle and at least one device external to the vehicle; monitor, via the OBD2 DLC port, one or more vehicle sensor data from one or more vehicular sensors tracking operational conditions of the vehicle; monitor, via the OBD2 DLC port, one or more operator input sensor data from one or more operator input sensors tracking operator input by an operator of the vehicle; analyze at least one of the monitored wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle or a combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised; based on a determination that vehicle operation has been compromised, alert the operator of the vehicle regarding the vehicle operation being compromised; and initiate one or more remediation operations, wherein the vehicle is an Internet of Things (“IoT”)-capable vehicle and the at least one device external to the vehicle comprises at least one IoT-capable device, wherein the wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle comprises machine-to-machine IoT communications, and the portable device is an IoT gateway through which all IoT communications pass, wherein initiating the one or more remediation operations comprises, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the machine-to-machine IoT communications and based on the operator action comprising disconnecting the portable device from the OBD2 DLC port, disrupting, with the portable device, communication between the at least one vehicle computing system and the at least one device external to the vehicle.
 15. The portable device of claim 14, wherein analyzing the combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data comprises analyzing the one or more vehicle sensor data and the one or more operator input sensor data to determine whether the one or more vehicle sensor data indicates operational conditions of the vehicle that are inconsistent with the corresponding one or more operator input sensor data.
 16. The portable device of claim 14, further comprising: a block-wireless-communications button; and a frequency jamming transmitter; wherein initiating the one or more remediation operations comprises, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the wireless communications and based on the operator action comprising depressing the block-wireless-communications button on the portable device, disrupting communication between the at least one vehicle computing system and the at least one device external to the vehicle by jamming, via the frequency jamming transmitter, all wireless communications within at least one set of telecommunications frequency ranges to and from the vehicle.
 17. The portable device of claim 14, further comprising: a restore button; wherein initiating the one or more remediation operations comprises, based on a determination that vehicle operation has been compromised by the at least one device external to the vehicle via the wireless communications and based on the operator action comprising depressing the restore button on the portable device, restoring settings and configurations for at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors, wherein the settings and configurations for the at least one of the one or more computing systems of the vehicle, the one or more vehicular sensors, or the one or more operator input sensors comprise one of factory settings and configurations or previously saved settings and configurations.
 18. The portable device of claim 14, wherein the set of instructions, when executed by the at least one processor, further causes the portable device to: encrypt the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data; and store the encrypted one or more vehicle sensor data and the encrypted one or more operator input sensor data in the data storage device of the portable device; wherein encrypting and storing the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data are performed either before or after analyzing the at least one of the monitored wireless communications between the at least one vehicle computing system and the at least one device external to the vehicle or the combination of the monitored one or more vehicle sensor data and the monitored one or more operator input sensor data, to determine whether vehicle operation has been compromised. 